Generating a virtual machines relocation protocol

ABSTRACT

Relocation of virtual machines is facilitated by obtaining, by a first controller, first power-related information from a first power system set that provides power to a first set of powered hardware components, where the first set of powered hardware components are running a first plurality of virtual machines. The first controller generates a relocation protocol for migrating the first plurality of virtual machines based, at least in part, upon the first power-related information. The relocation protocol includes: a migration of a first subset of one or more virtual machines so that the first subset of virtual machine(s) is to be migrated to and run on a second set of powered hardware components in a manner such that the first subset of virtual machine(s) continues to operation in a substantially continuous manner through the migration; and a snapshotting of a second subset of one or more virtual machines.

BACKGROUND

As known, a virtual machine (VM) is a software implementation of amachine (e.g., a computer) that executes computer programs. A VMtypically emulates a physical computing environment, with requests for acentral processing unit (CPU), memory, hard disk, and other hardwareresources being managed by a virtualization layer which translates theserequests to the underlying physical hardware. Virtual machines arecreated within a virtualization layer, such as a hypervisor or avirtualization platform that runs on top of a client or server operatingsystem. System migrations of virtual machines may be desired for avariety of reasons, including the ability to provide a backup systemwhile hardware and/or software upgrades are being installed. Systemmigrations may also be performed to move a virtual machine to a newprocessor or other hardware. There are a number of approaches toperforming the migration, including halting execution of a virtualmachine to perform the migration, as well as performing a livemigration, which migrates a virtual machine while it is executing. Livevirtual machine migration is often desired by companies with missioncritical systems.

Data center power outages can occur for a variety of reasons, includingnatural disasters. Natural disasters or other weather-related causeshave become a more frequent variable in the availability of datacenters. To ensure that a data center, including any virtual machinesrunning within the data center, can remain running while experiencing amain power outage, battery backup systems and gas-powered generators maybe used to continue to power the data center, for instance, tofacilitate an ordered shutdown and/or backup of running systems. In manycases, however, data may end of being lost due to inefficient backupmechanisms, or backup mechanisms that are never started, or that fail tocomplete before battery backup systems run out of energy, or backupgenerators run out of fuel.

SUMMARY

Shortcomings of the prior art are overcome and advantages are providedthrough the provision of a computer-implemented method which includesobtaining, by a first controller, first power-related information from afirst power system set including one or more first power systems thatprovide power to a first set of powered hardware components with whichthe first controller is associated. The first set of powered hardwarecomponents runs a first plurality of virtual machines, and the firstpower-related information includes an estimated amount of time to powerfailure to the first set of powered hardware components. The method alsoincludes determining, by the first controller, that the estimated amountof time to power failure is an insufficient amount of time tolive-migrate all virtual machines of the first plurality of virtualmachines; and obtaining, by the first controller, network power-relatedinformation from a power system providing power to a network with a datatransfer path from the first set of powered hardware components to asecond set of powered hardware components, where the power systemproviding power to the network is other than the one or more first powersystems providing power to the first set of powered hardware components.In addition, the method includes dynamically generating, by the firstcontroller, a relocation protocol for migrating the first plurality ofvirtual machines based, at least in part, upon the first power-relatedinformation and the network power-related information, the relocationprotocol being an emergency relocation protocol dynamically generatedbased, at least in part, on the estimated amount of time to powerfailure to the first set of powered hardware components beinginsufficient to live-migrate all virtual machines of the first pluralityof virtual machines. The generating includes assigning, by the firstcontroller, a virtual machine of the first plurality of virtual machinesto a first subset of one or more virtual machines of the first pluralityof virtual machines to be live migrated, or a second subset of one ormore virtual machines of the first plurality of virtual machines to besnapshotted for migration. The assigning is based, at least in part,upon the first power-related information and the network power-relatedinformation, including the estimated amount of time to power failure.The relocation protocol includes: a live migrating of the first subsetof one or more virtual machines of the first plurality of virtualmachines so that the first subset of virtual machine(s) is to bemigrated to and run on a second set of powered hardware components, thelive migration being in a manner such that the first subset of virtualmachine(s) continues to operate in a continuous manner through themigration; and a snapshotting of the second subset of the one or morevirtual machines of the first plurality of virtual machines at the firstset of powered hardware components. Further, the method includesmigrating the first plurality of virtual machines, using the relocationprotocol, to the second set of powered hardware components.

Advantageously, in one or more aspects, a computer-implemented method,system and computer program product are provided for facilitatingdynamic generation of a relocation protocol for virtual machines based,at least in part, upon power-related information obtained from, forinstance, a first power system set providing power to a first set ofpowered hardware components upon which the virtual machines run. Therelocation protocol for migrating the virtual machines may include: amigration of a first subset of one or more virtual machines so that thefirst subset of virtual machine(s) is to be migrated to run on a secondset of powered hardware components in a manner that the first subset ofvirtual machine(s) continues to operate in a substantially continuousmanner through the migration; and a snapshotting of a second subset ofone or more virtual machines of the virtual machines running on thefirst set of hardware components. By dynamically determining therelocation protocol, processing is better able to prioritize migrationof virtual machines to ensure a more efficient transfer of virtualmachines from, for instance, the first set of powered hardwarecomponents to the second set of powered hardware components. Thisrelocation protocol may seek to minimize or reduce loss of data due, forinstance, to a natural disaster occurring in the vicinity of the firstset of powered hardware components, causing an upcoming loss of power atthe first set of powered hardware components.

As explained further herein, generating the relocation protocol mayinclude referencing historical data relating to virtual machinemigration or virtual machine snapshotting to facilitate placing one ormore of the virtual machines in either the first or second subset ofvirtual machines. For instance, the historical data may includeinformation on a length of time required to live-migrate or snapshot avirtual machine of a particular type, workload size, etc.

Additionally, or alternatively, the relocation protocol may be generatedusing associated priority information of one or more of the virtualmachines to be migrated. For instance, in one or more embodiments, acustomer may pay for a higher priority of service in the event of apower failure, and thus, the one or more virtual machines running thatclient's workload may be identified for live-migration. Further,generating the relocation protocol may take into account the powerstatus of intermediate hardware components and data paths between, forinstance, a first data center and a second data center, any may eveninclude identifying the particular data center, or second set of poweredhardware components to which the virtual machines are to be migrated, aswell as the data path to be used.

In one or more implementations, the computer-implemented method furtherincludes: migrating the first subset of virtual machine(s) to the secondset of powered hardware components in a manner such that the first setof virtual machine(s) continues to operate in a substantially continuousmanner through the migration; and migrating the second subset of virtualmachine(s) by, at least in part, deploying the second subset of virtualmachine(s) to the second set of powered hardware components based on arespective snapshot(s) of the second subset of virtual machine(s)obtained at the first set of powered hardware components. By way ofexample, the migrating of the second subset of virtual machine(s) may beperformed after completion of the migrating of the first subset ofvirtual machine(s).

In one or more embodiments, the migrating of the second subset ofvirtual machine(s) may include first transferring the respectivesnapshot(s) of the virtual machine(s) of the second subset of virtualmachine(s) to an intermediary set of powered hardware components poweredby an intermediary power system set, that is, before deploying thesecond subset of virtual machine(s) to the second set of poweredhardware component(s), based on the respective snapshot(s). In suchembodiments, the intermediary power system set is different from thefirst power system set, and the transferring of the respectivesnapshot(s) of the virtual machine(s) of the second subset of virtualmachine(s) to the intermediary set of powered hardware components mayoccur substantially simultaneous with the migrating of the first subsetof virtual machine(s) to the second set of powered hardware components.

In one or more implementations, the first set of powered hardwarecomponents are of a first cloud, and the first controller is a firstcloud controller, and the second set of powered hardware components areof a second cloud. The second set of hardware components may be poweredfrom a second power system set including one or more second powersystems. In one or more embodiments, the first cloud and second cloudmay be hosted in different, geographically-separated data centers.

Further, in one or more implementations, the second cloud may include asecond cloud controller, and generating, by the first controller, therelocation protocol, may include obtaining, by the first cloudcontroller, second power-related information from the second cloudcontroller or the second power system set indicative of power status tothe second set of powered hardware components.

In one or more embodiments, generating, by the first controller, therelocation protocol may include referencing historical data relating toat least one of virtual machine migration or virtual machinesnapshotting to facilitate placing at least one virtual machine of thefirst plurality of virtual machines in either the first subset ofvirtual machine(s) or the second subset of virtual machine(s).

In addition, in one or more embodiments, generating, by the firstcontroller, the relocation protocol may include using associatedpriority information of at least one virtual machine of the firstplurality of virtual machines, and placing the at least one virtualmachine in either the first subset of virtual machine(s) or the secondsubset of virtual machine(s).

In one or more embodiments, generating by the first controller therelocation protocol may include evaluating a data transfer path from thefirst set of powered hardware components to the second set of poweredhardware components. The evaluating the data transfer path may includedetermining power status to one or more switches in the data transferpath to, for instance, confirm continued availability of the datatransfer path.

Systems and computer program products relating to one or more aspectsare also described and claimed herein. Further, services relating to oneor more embodiments may also be described and claimed herein.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more aspects of the present invention are particularly pointedout and distinctly claimed as examples in the claims at the conclusionof the specification. The foregoing and other objects, features, andadvantages of the invention are apparent from the following detaileddescription taken in conjunction with the accompanying drawings inwhich:

FIG. 1 depicts an example of a virtual computing environment havingvirtual machines that may undergo a relocation protocol, in accordancewith one or more aspects of the present invention;

FIG. 2A depicts one embodiment of a transfer of virtual machines from afirst set of powered hardware components to a second set of poweredhardware components, using a generated relocation protocol, inaccordance with one or more aspects of the present invention;

FIG. 2B depicts one embodiment of a process for generating a relocationprotocol for migrating a first plurality of virtual machines from, forinstance, the first set of powered hardware components to the second setof powered hardware components of FIG. 2A, in accordance with one ormore aspects of the present invention;

FIG. 3A depicts another embodiment of a transfer of virtual machinesfrom a first set of powered hardware components, or source system, to asecond set of powered hardware components, or target system, using agenerated relocation protocol which includes live-migrating one or morevirtual machines and snapshotting one or more other virtual machines, inaccordance with one or more aspects of the present invention;

FIGS. 3B & 3C depict one embodiment of a process for generating arelocation protocol for live-migrating one or more virtual machines fromthe source system to the target system of FIG. 3A, and snapshotting oneor more other virtual machines of the source system for subsequentdeployment on the target system, in accordance with one or more aspectsof the present invention;

FIG. 4A depicts another example of a computing environment, which mayincorporate and use one or more aspects of the present invention;

FIG. 4B depicts further details of the memory of FIG. 4A, in accordancewith one or more aspects of the present invention;

FIG. 5 depicts a further embodiment of a computing system which mayincorporate virtual machine relocation processing, in accordance withone or more aspects of the present invention;

FIG. 6 depicts one embodiment of a cloud computing environment, whichmay facilitate implementing, or be used in association with, one or moreaspects of the present invention; and

FIG. 7 depicts an example of extraction model layers, which mayfacilitate implementing relocating of virtual machines, in accordancewith one or more aspects of the present invention.

DETAILED DESCRIPTION

Previously, virtual machines might be migrated from one data center toanother data center as a disaster avoidance solution. For instance, themigrated data may be secondary backup data that has been migrated.However, such data is not as up-to-date as the running virtual machineslocated in the primary location. Further, there would typically be noway to ascertain whether the second data center location is also beingaffected by the disaster that is jeopardizing data in the primary,source location.

Therefore, disclosed herein, in one or more aspects, is an efficient useof correlating available runtime power at, for instance, a source systemfor a first cloud, with time required to evacuate the cloud to avoidsystem downtime. In particular, disclosed herein in various aspects areapproaches for a cloud manager to use information made available from,for instance, a data center disaster recovery application, to determineappropriate action to take for its virtual machines. For instance, inone or more embodiments, data center disaster recovery information andhistoric information about virtual machines may be used to determinewhich action is appropriate for each virtual machine, such aslive-migrating, snapshotting, or even shutting down a particular virtualmachine. By way of example, this may include using historic informationon time required for each of the possible actions by a particularvirtual machine type or workload size. This includes, for instance, thetype of application running on the virtual machine, the type of virtualmachine, and the hardware that the virtual machine is running on. In oneor more other aspects, using historic information on the times requiredto transfer the results of each action may be considered. For instance,time to snapshot and send a snapshot versus time to live-migrate aparticular virtual machine, might be ascertained. This might alsoinclude considering available information about the transfer path from,for instance, the first data center to the second data center. Further,generating the relocation protocol may include selecting the second datacenter based, for instance, on power availability to the second datacenter. This may include, for instance, communicating with a secondcontroller of the second data center and/or a second power system setpowering the second data center, to determine availability of power atthe second data center. Further, this may include taking into accountdata center disaster recovery information about participants (e.g.,switches or other hardware) in the transfer path. For example, is theresufficient power, and thus time, available in the data transfer path toallow the migration or transfer to occur? Also, historic information onperformance impacts of recovery status may be considered in generatingthe relocation protocol.

Analytics may be employed to determine an amount of time remaining, forinstance, on a backup generator during a disaster scenario, before thebackup generator goes down through, for instance, analysis of historicinformation. This analysis may include, for instance, evaluating anamount of gas in a generator, and determining that that amount of gasmay last a certain amount of hours before the system loses powercompletely.

Disclosed herein is the concept of accounting for situations where thereis isn't enough time to live-migrate all of the virtual machines, andinstead generate a protocol to take snapshots of selected virtualmachines to ensure that nothing is lost, and thereby protecting the mostcurrent state of the virtual machines from being lost in the event thatthere is insufficient power to the source data center or resourcesavailable to live-migrate all the virtual machines. Analytics that takeinto account historical migration times from one virtual machine toanother virtual machine could be used to determine if there is time toperform the migration, and in the situations where the generator wouldrun out of power before the migration could complete, a snapshot of thevirtual machine could be taken preemptively to avoid data loss. Thedecision to create a snapshot could be done by an administrator, or itcould be set to process automatically, for instance, in cases where theadministrator is unavailable. In this way, a new virtual machine couldbe spun up to the precise state from before power loss, with no loss ofdata.

Thus, in accordance with one or more aspects, a relocation protocol,such as an emergency relocation protocol, is dynamically generated fortransferring virtual machines from, for instance, a first set of poweredhardware components (such as a first (or source) system or data center),to a second set of powered hardware components (such as a second (ortarget) system or data center). The relocation protocol may use, in oneor more embodiments, both live migration of a first subset of one ormore virtual machines of the virtual machines to be transferred, and asnapshotting of a second subset of one or more virtual machines of thevirtual machines to be transferred. The relocation protocol may bedynamically generated based, at least in part, on power-relatedinformation obtained from a first power system set of one or more firstpower systems providing power to, for example, the first set of poweredhardware components running the plurality of virtual machines.

In certain embodiments, the first set of hardware components are of afirst cloud, the first controller is a first cloud controller, and thesecond set of powered hardware components are of a second cloud. Thesecond set of powered hardware components are powered from a secondpower system set including one or more second power systems, where thesecond power system set may be different from the first power systemset. By way of example, the first cloud and the second cloud may behosted in different, geographically-separated data centers. Further, asdescribed below, one or more intermediary systems, such as one or moreintermediary sets of powered hardware components, may be employed tofacilitate simultaneous live migration of the first subset of virtualmachine(s) and transfer of the respective snapshot(s) of the secondsubset of virtual machine(s), for instance, across different data pathsfrom the first set of powered hardware components.

In one or more embodiments, the first power-related information includesan estimated amount of time to power failure to the first set of poweredhardware components, and the relocation protocol is an emergencyrelocation protocol, dynamically generated based, at least in part, onthe amount of time to power failure to the first set of powered hardwarecomponents. By way of example, generating, by the first controller, therelocation protocol may include referencing historical data relating to,for instance, live-migrating of one or more virtual machines and/orsnapshotting of one or more virtual machines. For instance, thehistorical data may include information on the amount of time requiredto live-migrate a particular virtual machine type or workload size, aswell as an amount of time to snapshot a particular virtual machine typeor workload. Based on this information, the generating may dynamicallydetermine an appropriate relocation protocol in view of, for instance,the amount of time remaining to power failure to the first set ofpowered hardware components.

Alternatively, or additionally, generating, by the first controller, therelocation protocol may include using or referencing associated priorityinformation of one or more virtual machines of the first plurality ofvirtual machines, and placing the one or more virtual machines in eitherthe first subset of virtual machine(s) or the second subset of virtualmachine(s) based on the priority information. For instance, clients maysubscribe at different levels of priority should an emergency relocationof their workload be required. For instance, a client subscribing at a“Gold Level” may ensure that the virtual machines running its workloadbe live-migrated from the first set of powered hardware components tothe second set of powered hardware components, at least as priority overclients at lower levels of subscription. In such an implementation, thevirtual machines associated with the lower levels of subscription may besnapshotted for subsequent deployment on the second set of poweredhardware components based, for instance, on the estimated amount of timeto power failure.

More particularly, some embodiments of the present invention may includeone, or more, of the following features, characteristics, operations,and/or advantages: (i) managing, by a first cloud controller, a firstset of power system(s) that provide power to a first set of poweredhardware component(s) of a first cloud, with the first set of poweredcomponent(s) running a first plurality of virtual machines (VMs); (ii)receiving, by the first cloud controller, and from a first power systemof the first set of powered system(s), a first item of power-relatedinformation; (iii) determining, by the first cloud controller, aprocedure for safely migrating the first plurality of VMs based, atleast in part, upon the first item of power-related information; (iv)determination of the procedure for safely migrating the first set of VMsincludes: (a) migrating a first subset of VM(s) of the first pluralityof VMs so that the first subset of VM(s) to run on a second set ofpowered hardware component(s) in a manner such that the first subset ofVM(s) continue to operate in a substantially continuous manner throughthe migration, and (b) snapshotting a second subset of VM(s) of thefirst plurality of VMs; (v) migrating of the first subset of VM(s) ofthe first plurality of VMs so that the first subset of VM(s) to run on asecond set of powered components in a manner such that the first set ofVM(s) continues to operate in a substantially continuous manner throughthe migration; (vi) migrating the second set of VM(s) by deploying themto the second set of powered hardware component(s) based on theirrespective snapshots; (vii) the migration of the second set of VM(s) maybe performed after completion of the migration of the first set ofVM(s); (viii) the process does not require adding networks to offloadwork to another VM; (ix) the process looks at the other VMs available ina network and migrates the work to the optimal location; (x) the processsnapshots preemptively so data replication isn't necessary; and/or (xi)the process responds during a disaster to prevent a need for therecovery of data.

One example of a computing environment to incorporate and use one ormore aspects of a virtual machine relocation facility such as disclosedherein is initially described with reference to FIG. 1. Referring toFIG. 1, in one example, a computing environment 100 may be based on thez/Architecture, offered by International Business Machines (IBM®)Corporation, Armonk, N.Y. The z/Architecture is described in an IBMPublication entitled “z/Architecture—Principles of Operation,”Publication No. SA22-7832-10, 11 Edition, March 2015, which is herebyincorporated by reference herein in its entirety. Z/ARCHITECTURE, IBM,Z/VM and Z/OS (referenced herein) are registered trademarks ofInternational Business Machines Corporation, Armonk, New York. Othernames used herein may be registered trademarks, trademarks or productnames of International Business Machines Corporation or other companies.

In another example, the computing environment may be based on the PowerArchitecture, offered by International Business Machines Corporation,Armonk, New York. One embodiment of the Power Architecture is describedin “Power ISA™ Version 2.07B,” International Business MachinesCorporation, Apr. 9, 2015, which is hereby incorporated herein byreference in its entirety. POWER ARCHITECTURE is a registered trademarkof International Business Machines Corporation, Armonk, N.Y., USA.

In yet a further example, the computing environment may be based onother architectures offered by International Business MachinesCorporation and/or other companies.

Computing environment 100 includes a central processor complex (CPC) 102providing virtual machine support. CPC 102 is coupled to one or moreinput/output (I/O) devices 106 via one or more control units 108.Central processor complex 102 includes, for instance, a processor memory104 (a.k.a., main memory, main storage, central storage) coupled to oneor more central processors (a.k.a., central processing units (CPUs))110, and an input/output subsystem 111, each of which is describedbelow.

Processor memory 104 includes, for example, one or more virtual machines112, a virtual machine manager, such as a hypervisor 114 that managesthe virtual machines, and processor firmware 115. One example ofhypervisor 114 is z/VM®, offered by International Business MachinesCorporation, Armonk, New York. The hypervisor is sometimes referred toas the host. Further, as used herein, firmware includes, e.g., themicrocode and/or millicode of the processor. It includes, for instance,the hardware-level instructions and/or data structures used inimplementation of higher level machine code. In one embodiment, itincludes, for instance, proprietary code that is typically delivered asmicrocode that includes trusted software or microcode specific to theunderlying hardware and controls operating system access to the systemhardware.

The virtual machine support of the CPC provides the ability to operatelarge numbers of virtual machines 112, each capable of operating withdifferent programs 122 and running a guest operating system 120, such asLinux. Each virtual machine 112 is capable of functioning as a separatesystem. That is, each virtual machine can be independently reset, run aguest operating system, and operate with different programs. Anoperating system or application program running in a virtual machineappears to have access to a full and complete system, but in reality,only a portion of it is available.

Processor memory 104 is coupled to central processors (CPUs) 110, whichare physical processor resources assignable to virtual machines. Forinstance, virtual machine 112 includes one or more logical processors,each of which represents all or a share of a physical processor resource110 that may be dynamically allocated to the virtual machine.

Further, processor memory 104 is coupled to an I/O subsystem 111.Input/output subsystem 111 directs the flow of information betweeninput/output control units 108 and devices 106 and main storage 104. Itis coupled to the central processing complex, in that it can be a partof the central processing complex or separate therefrom.

By way of example, one or more computing environments such as depictedin FIG. 1 may be present within a data center, and as noted, data centerpower outages can occur for a variety of reasons, including naturaldisasters. To ensure that a data center, including any virtual machinesrunning on systems within a data center, can remain running whileexperiencing a main power outage, battery backup systems and/orgas-powered generators may be used to continue to power the data center,at least, for a period of time to, for instance, facilitate an orderedshutdown and/or backup of running systems. In the case of a naturaldisaster, main power may be out for several days or even weeks.Therefore, disclosed herein, in one or more aspects, is a process fordynamically generating a relocation protocol to relocate virtualmachines of a data center to, for instance, another, remote data center,to allow for continued operation of the virtual machines.

FIG. 2A depicts one embodiment of a process for transferring virtualmachines from a first set of powered hardware components 200, such as asource system, or source data center, to a second set of poweredhardware components 220, such as a target system, or target data center.First set of powered hardware components 200 is powered by a first powersystem set 201 of one or more first power systems, and second set ofpowered hardware components 220 is powered by a second power system set221 of one or more second power systems. In practice, the first andsecond power system sets 201, 221 are, at least in part, different setsof power systems. As shown, first set of powered hardware components 200may include a first cloud environment 210 and second set of poweredhardware components 220 may include a second cloud environment 230.First cloud 210 may have a first cloud controller 211, and second cloud230 a second cloud controller 231. As illustrated, first cloud 210 mayalso include a plurality of virtual machines 212 running on first set ofpowered hardware components 200.

As disclosed herein, a controller, such as first cloud controller 211,may be provided with the ability to obtain and leverage data from one ormore power systems, such as first power system set 201 and second powersystem set 221, to dynamically determine or generate a relocationprotocol, including where and how to safely evacuate the virtualmachines of the associated system, such as first set of powered hardwarecomponents 220. This may be particularly beneficial where a naturaldisaster has occurred which has taken out main power to the first set ofpowered hardware components 200, and where limited backup power timeremains.

As disclosed herein, the controller is provided with a facility orcapability to generate a relocation protocol for migrating the pluralityof virtual machines 212 based, at least in part, upon power-relatedinformation (e.g., first power-related information) obtained from atleast the first power system set 201. For instance, the power-relatedinformation may include an amount of time remaining before power to thefirst set of powered hardware components 200 is lost. The relocationprotocol may include a migration of a first subset of one or morevirtual machines (e.g., virtual machine 1 in FIG. 2A) of the pluralityof virtual machines 212 so that the first set of virtual machine(s) isto be migrated to and run on the second set of powered hardwarecomponents 220 in a manner such that the first subset of virtualmachine(s) continues to operate in a substantially continuous mannerthrough the migration. This migration refers to a live-migration, whichis a process of moving a running virtual machine or application betweendifferent physical machines without disconnecting the client orapplication. Memory, storage, and network connectivity of the virtualmachine are transferred from an original machine (e.g., first set ofpowered hardware components 200) to a destination or target machine(e.g., second set of powered hardware components 220). Pre-copy orpost-copy memory migration may be employed, and various virtual machine(VM) managers provide live-migration support, as well as various cloudplatforms and systems available in the art. By way of specific example,the IBM® POWER Hypervisor™ provides live-migration support.

Additionally, the generated relocation protocol includes a snapshottingof a second subset of one or more virtual machines (e.g., virtualmachine 2, virtual machine 3 in FIG. 2A) of the plurality of virtualmachines 212. As known, a snapshot preserves the state and data of avirtual machine at a specific point in time. The state includes thevirtual machine's power state (for instance, powered on, powered off, orsuspended). The data include all the files that make up the virtualmachine. This includes disks, memory, and other devices, such as virtualnetwork interface cards. A virtual machine provides several options forcreating and managing snapshots and snapshot chains. These operationslet the controller create snapshots, revert to any snapshot in thechain, and remove snapshots. Snapshotting is currently supported byvarious virtual machine (VM) managers, such as with various VMware,Inc., machines. Additionally, snapshotting is supported by various IBMproducts, including IBM Virtual Servers™ and IBM Cloud Manager™.

In general, the time to create a snapshot and transfer a snapshot from asource system to a target or destination system may be considerably lessthan the time required to live-migrate a virtual machine from the sourcesystem to the destination system. Thus, the power-related informationfrom the first set of power system(s) 201, such as the amount of timepower will remain available to first set of powered hardware components200, may be used by cloud controller 211 in generating the relocationprotocol to ensure that substantially all virtual machines are eithermigrated to the second set of powered hardware components, orsnapshotted for transfer to and subsequent deployment at the second setof hardware components.

FIG. 2B depicts one embodiment of a process for dynamically generating arelocation protocol, and then transferring or migrating virtualmachines, for instance, during a disaster emergency where virtualmachines are to be transferred from one data center to another, remotedata center.

Referring to FIG. 2B, the process includes managing, by a first cloudcontroller, a first power system set providing power to a first set ofpowered hardware components of a first cloud, with a first set ofpowered hardware components running a first plurality of virtualmachines 270. The first cloud controller receives or obtains from afirst power system of the first power system set a first power-relatedinformation 275. As noted, this information may include, for instance,an amount of time power is to remain available to the first set ofpowered hardware components.

The first cloud controller then generates or determines a location and aprotocol for safely migrating the first plurality of virtual machinesbased, at least in part, upon the power-related information obtained280. The relocation protocol may include: a migration of a first subsetof virtual machine(s) of the first plurality of virtual machines so thatthe first subset of virtual machine(s) is to run on a second set ofpowered hardware components in a manner such that the first subset ofvirtual machine(s) continue to operation in a substantially continuousmanner through the migration 281; and preemptively snapshotting a secondsubset of virtual machine(s) of the first plurality of virtual machines282. The processing may further include migrating the first subset ofvirtual machine(s) of the first plurality of virtual machines so thatthe first subset of virtual machine(s) continue to operate in asubstantially continuous manner through the migration 285. Further, thesecond subset of virtual machine(s) may be migrated based on theirrespective snapshots (for instance, by deploying the second subset ofvirtual machine(s) to the second set of powered hardware componentsafter completion of migrating of the first subset of virtual machine(s))290.

In one or more aspects, the processing disclosed herein is based on aglobal migratory view, with the cloud controller working with othersystems, such as other cloud controllers and other power systems, tolook at the availability and efficacy of the systems that it isconnected to for migration of the virtual machines. For instance, in thesituation where workloads are running in a cloud environment that ispotentially going to go down due to, for instance, a loss of power,virtual machines may be migrated to a target or destination cloud thatis not failing. In such a case, migration may require quiescing of thevirtual machines that are to be moved to the new target cloud, andtransferring the data (memory, process state, etc.) to the target cloud.This work may take priority from a bandwidth viewpoint to avoid havingthe power drop out from under the running virtual machines. In addition,in parallel, virtual machines that are not going to be able to belive-migrated to the target environment may be snapshotted, capturingand saving their state to, for example, disk, in a manner that won'timpact the migration of the live virtual machines. Along with beingsnapshotted, these virtual machines would be shut down until subsequentdeployment on the target system.

In one or more embodiments, the controller, such as the cloud controllerdiscussed above, may weigh a number of factors in generating or decidingupon a particular relocation protocol for the virtual machines withwhich they are associated. These factors may include determining whatactions to take, rather than defaulting to either a migrating protocolvia pure migration and shutting down, including the option to snapshotone or more of the running virtual machines for transfer. The controllerselects or establishes which of the virtual machines are going to bemigrated, and which would instead be snapshotted, with the snapshotbeing transferred to the target or destination system. By way ofexample, this could include evaluating the historic time to snapshot avirtual machine of a particular type, the resulting size of thesnapshot, and the available bandwidth to transmit the snapshot. Further,the cloud controller could examine if the snapshot can be transmitted toan intermediate system or node using, for instance, data paths thatwould use bandwidth not needed for the migration of one or more othervirtual machines. In this manner, the transferred snapshots maysubsequently be transferred to the target or destination system forrecovery or deployment. Further, the cloud controller may ensure thatall transfer nodes (since multiple nodes could be used) are notthemselves being evacuated by communicating with the transfer node'scloud controller. If they themselves are also being evacuated, then thecontroller would look for alternate nodes, such as alternateintermediate nodes, and if none are available, may negotiate with one orother cloud controllers to determine if it will remain running longenough to be used as a transfer node. For intermediate hardware, such asintermediate switches to be used in the transfer, that is, switches inthe data path, the cloud controller may work with a cloud controllerthat the intermediate hardware is associated with, or if they areindependent, may communicate with the power system directly that isassociated with the intermediate hardware. While the migration of one ormore virtual machines is being performed, the one or more virtualmachines to be snapshotted may be snapshotted in parallel, and thentransferred to the target or destination node, system, data center, etc.

FIG. 3A depicts a more detailed example of virtual machine migrationfrom, for instance, a source system 300 to a target system 330, whichmay use, in part, one or more intermediate systems 350. In thisembodiment, source system 300, such as a first set of powered hardwarecomponents, includes a first cloud 310 with a plurality of virtualmachines 312 running, and having an associated control 311. Sourcesystem 300 is powered by a first power system set (power system(s) A301), that includes one or more power systems. The migration of thevirtual machines 312 is to occur across a network 320 that may includeone or more intermediate hardware components, such as switches 322, 326,each of which is powered by an associated power system set (such aspower system(s) B 324, power system(s) C 328), each of which may includeone or more power systems.

In this example, target system 330, such as a second set of poweredhardware components, may host a second cloud environment 340 which has asecond control 341 associated therewith. Target system 330 may also bepowered by a second power system set (e.g., power system(s) D 331) ofone or more power systems. As noted, one or more intermediate systems350 may be employed, for example, to facilitate the simultaneoustransfer of snapshotted data at the time that one or more virtualmachines are being migrated, for instance, across different data paths321, 325. Intermediate system 350 may include, in one or more examples,memory 360 for receiving virtual machine snapshots 362, and anassociated control 361. Intermediate system(s) 350 may be powered by anintermediate power system set (e.g., power system(s) E 351), which mayinclude one or more power systems. In general, the power system sets,such as power system(s) A 301, power system(s) B 324, power system(s) C328, power system(s) D 331, and power system(s) E 351, may include or bedifferent sets of power systems or, in one or more other embodiments,one or more of them may have the same power system(s), such as powersystem(s) B 324 and power system(s) C 328 of network 320.

FIGS. 3B & 3C depict one embodiment of a process for migrating virtualmachines, in accordance with one or more aspects of the presentinvention. Referring collectively to FIGS. 3A-3C, a power failurenotification may be received from power system(s) A 301 to the sourcesystem 370, such as at first cloud control 311. Based on this, the firstcloud controller or manager determines where to migrate the virtualmachines to, that is, determines the target or destination system (orsecond set of powered hardware components) 372.

In one or more embodiments, the cloud controller manager 311 may querypower systems, such as power system(s) B 324 providing power to switch 1322 in data path 321, between the source system and the target system374. Additionally, the cloud control or manager 331 of source system 300may determine the status of power system(s) D 331 providing power to thetarget system 376. This may involve the first cloud control 311 queryingthe second cloud control 341 of target system 330 or, may involve thecloud control 311 communicating directly with power system(s) D 331 toobtain the desired information.

Next, in one or more embodiments, the cloud control 311 may determineone or more intermediate systems or nodes that may accommodatesnapshotted data, as well as the status of the power system(s) E 351 tothe intermediate system(s) 378. Along with this information, the cloudcontrol or manager may determine the status of power system(s) C 328powering one or more switches 326 in a data path 325 between the sourcesystem and the intermediate system(s) 380. With this information, alongwith other information, such as historical information on time requiredto migrate a virtual machine, or snapshot a virtual machine, or prioritydata where one or more virtual machines of the source system areindicated to the cloud control as having a higher priority, andtherefore, to have priority for live-migrating as opposed to beingsnapshotted, or any other type of data which may be available to thecloud control in deciding whether to place a particular virtual machine312 into a first subset or a second subset of virtual machines of therelocation protocol 382. Once the virtual machine relocation protocol isgenerated, then the protocol may be implemented 384, which completes theprocessing 386. One embodiment for implementing a virtual machinerelocation protocol 384 such as described herein is depicted in FIG. 3C.

As illustrated in FIG. 3C, implementing the relocation protocol mayinclude live-migrating one or more virtual machines (e.g., virtualmachine 1 in the example of FIG. 3A) from the source system to thetarget system, for instance, via one or more switch(es) 1 within a datapath between the source and target systems 390. In combination with thelive-migrating of one or more virtual machines, processing includessnapshotting one or more virtual machines (e.g., virtual machine 2,virtual machine 3) of the source system 392. In one or moreimplementations, the snapshotting process may be at a lower prioritythan the live-migration process. Also, in one or more other embodiments,the snapshotting may occur in parallel with the migrating of one or morevirtual machines. The snapshot data is forwarded from the source system(for instance, to one or more intermediate systems via one or more datapaths), which may include one or more hardware components such asswitches 394. After the virtual machine snapshots have been transferredfrom the intermediate system(s) to the target, destination system, theymay be deployed at the target system 396.

Another embodiment of a computing environment which may incorporate anduse one or more aspects of the virtual machine relocation facilitydescribed herein is depicted in FIG. 4A. In this example, a computingenvironment 400 includes, for instance, a native central processing unit(CPU) 402, a memory 404, and one or more input/output devices and/orinterfaces 406 coupled to one another via, for example, one or morebuses 408 and/or other connections. As examples, computing environment400 may include a PowerPC processor or a Power Systems server offered byInternational Business Machines Corporation, Armonk, N.Y.; an HPSuperdome with Intel Itanium II processors offered by Hewlett PackardCo., Palo Alto, Calif.; and/or other machines based on architecturesoffered by International Business Machines Corporation, Hewlett Packard,Intel, Oracle, or others.

Native central processing unit 402 includes one or more native registers410, such as one or more general purpose registers and/or one or morespecial purpose registers used during processing within the environment.These registers include information that represents the state of theenvironment at any particular point in time.

Moreover, native central processing unit 402 executes instructions andcode that are stored in memory 404. In one particular example, thecentral processing unit may execute emulator code 412 stored in memory404. This code enables the computing environment configured in onearchitecture to emulate one or more other architectures. For instance,emulator code 412 allows machines based on architectures other than thez/Architecture, such as PowerPC processors, Power Systems servers, HPSuperdome servers or others, to emulate the z/Architecture® (and/orESA/390) and to execute software and instructions developed based on thez/Architecture®.

Further details relating to emulator code 412 are described withreference to FIG. 4B. Guest instructions 450 stored in memory 404comprise software instructions (e.g., correlating to machineinstructions) that were developed to be executed in an architectureother than that of native CPU 402. For example, guest instructions 450may have been designed to execute on a z/Architecture® processor, butinstead, are being emulated on native CPU 402, which may be, forexample, an Intel Itanium II processor. In one example, emulator code412 includes an instruction fetching routine 452 to obtain one or moreguest instructions 450 from memory 404, and to optionally provide localbuffering for the instructions obtained. It also includes an instructiontranslation routine 454 to determine the type of guest instruction thathas been obtained and to translate the guest instruction into one ormore corresponding native instructions 456. This translation includes,for instance, identifying the function to be performed by the guestinstruction and choosing the native instruction(s) to perform thatfunction.

Further, emulator code 412 includes an emulation control routine 460 tocause the native instructions to be executed. Emulation control routine460 may cause native CPU 402 to execute a routine of native instructionsthat emulate one or more previously obtained guest instructions and, atthe conclusion of such execution, return control to the instructionfetch routine to emulate the obtaining of the next guest instruction ora group of guest instructions. Execution of the native instructions 456may include loading data into a register from memory 404; storing databack to memory from a register; or performing some type of arithmetic orlogic operation, as determined by the translation routine.

Each routine is, for instance, implemented in software, which is storedin memory and executed by native central processing unit 402. In otherexamples, one or more of the routines or operations are implemented infirmware, hardware, software or some combination thereof. The registersof the emulated processor may be emulated using registers 410 of thenative CPU or by using locations in memory 404. In embodiments, guestinstructions 450, native instructions 456 and emulator code 412 mayreside in the same memory or may be disbursed among different memorydevices.

Exemplary embodiments of further computing environments to implement oneor more aspects of the present invention are described below withreference to FIGS. 5-7.

By way of further example, FIG. 5 depicts one embodiment of a computingenvironment 500, which includes a computing system 512. Examples ofwell-known computing systems, environments, and/or configurations thatmay be suitable for use with computer system 512 include, but are notlimited to, a desktop computer, a workstation, a handheld or laptopcomputer or device, a mobile phone, a programmable consumer electronicdevice, a tablet, a personal digital assistant (PDA), and the like.

Computing system 512 may be described in the general context of computersystem-executable instructions, such as program modules, being executedby a computer system. Generally, program modules may include routines,programs, objects, components, logic, data structures, and so on thatperform particular tasks or implement particular abstract data types.

As depicted in FIG. 5, computing system 512, is shown in the form of ageneral-purpose computing device. The components of computing system 512may include, but are not limited to, one or more processors orprocessing units 516, a system memory 523, and a bus 518 that couplesvarious system components including system memory 523 to processor 516.

In one embodiment, processor 516 may be based on the z/Architecture®offered by International Business Machines Corporation, or otherarchitectures offered by International Business Machines Corporation orother companies. z/Architecture® is a registered trademark ofInternational Business Machines Corporation, Armonk, N.Y., USA. Oneembodiment of the z/Architecture® is described in “z/Architecture®Principles of Operation,” IBM Publication No. SA22-7832-10, March 2015,which is hereby incorporated herein by reference in its entirety.

In other examples, it may be based on other architectures, such as thePower Architecture offered by International Business MachinesCorporation. One embodiment of the Power Architecture is described in“Power ISA™ Version 2.07B,” International Business Machines Corporation,Apr. 9, 2015, which is hereby incorporated herein by reference in itsentirety. POWER ARCHITECTURE is a registered trademark of InternationalBusiness Machines Corporation, Armonk, New York, USA. Other names usedherein may be registered trademarks, trademarks, or product names ofInternational Business Machines Corporation or other companies.

Bus 518 represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnect (PCI) bus.

Computing system 512 may include a variety of computer system readablemedia. Such media may be any available media that is accessible bycomputing system 512, and it includes both volatile and non-volatilemedia, removable and non-removable media.

System memory 523 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 530 and/or cachememory 532. Computing system 512 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 534 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media could be provided.In such instances, each can be connected to bus 518 by one or more datamedia interfaces. As described below, memory 523 may include at leastone program product having a set (e.g., at least one) of program modulesthat are configured to carry out the functions of embodiments of theinvention.

Program/utility 540, having a set (at least one) of program modules 542,may be stored in memory 532 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 542 generally carry out the functionsand/or methodologies of embodiments of the invention as describedherein. Alternatively, a separate, virtual machine relocation control,system, module, logic, etc., 501 may be provided within computingenvironment 512.

Computing system 512 may also communicate with one or more externaldevices 514 such as a keyboard, a pointing device, a display 524, etc.;one or more devices that enable a user to interact with computing system512; and/or any devices (e.g., network card, modem, etc.) that enablecomputing system 512 to communicate with one or more other computingdevices. Such communication can occur via Input/Output (I/O) interfaces522. Still yet, computing system 512 can communicate with one or morenetworks such as a local area network (LAN), a general wide area network(WAN), and/or a public network (e.g., the Internet) via network adapter520. As depicted, network adapter 520 communicates with the othercomponents of computing system, 512, via bus 518. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computing system 512.Examples, include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

One or more aspects may relate to or use cloud computing.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of certainteachings recited herein are not limited to a cloud computingenvironment. Rather, embodiments of the present invention are capable ofbeing implemented in conjunction with any other type of computingenvironment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

A cloud computing node may include a computer system/server, such as theone depicted in FIG. 5. Computer system/server 512 of FIG. 5 may bepracticed in distributed cloud computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed cloud computing environment,program modules may be located in both local and remote computer systemstorage media including memory storage devices. Computer system/server512 is capable of being implemented and/or performing any of thefunctionality set forth hereinabove.

Referring now to FIG. 6, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 6 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring to FIG. 7, a set of functional abstraction layers provided bycloud computing environment 50 is shown. It should be understood inadvance that the components, layers, and functions shown in FIG. 7 areintended to be illustrative only and embodiments of the invention arenot limited thereto. As depicted, the following layers and correspondingfunctions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and processing unit (PU) virtual machinerelocation processing 96.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinaryskills in the art without departing from the scope and spirit of thedescribed embodiments. The terminology used herein was chosen to bestexplain the principles of the embodiments, the practical application ortechnical improvement over technologies found in the marketplace, or toenable others of ordinary skills in the art to understand theembodiments disclosed herein.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprise” (andany form of comprise, such as “comprises” and “comprising”), “have” (andany form of have, such as “has” and “having”), “include” (and any formof include, such as “includes” and “including”), and “contain” (and anyform contain, such as “contains” and “containing”) are open-endedlinking verbs. As a result, a method or device that “comprises”, “has”,“includes” or “contains” one or more steps or elements possesses thoseone or more steps or elements, but is not limited to possessing onlythose one or more steps or elements. Likewise, a step of a method or anelement of a device that “comprises”, “has”, “includes” or “contains”one or more features possesses those one or more features, but is notlimited to possessing only those one or more features. Furthermore, adevice or structure that is configured in a certain way is configured inat least that way, but may also be configured in ways that are notlisted.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below, if any, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of the present invention has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the invention in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The embodiment was chosen and described in order to best explain theprinciples of one or more aspects of the invention and the practicalapplication, and to enable others of ordinary skill in the art tounderstand one or more aspects of the invention for various embodimentswith various modifications as are suited to the particular usecontemplated.

What is claimed is:
 1. A computer-implemented method comprising: obtaining, by a first controller, first power-related information from a first power system set comprising one or more first power systems powering a first set of powered hardware components with which the first controller is associated, the first set of powered hardware components running a first plurality of virtual machines, and the first power-related information including an estimated amount of time to power failure to the first set of powered hardware components; determining, by the first controller, that the estimated amount of time to power failure is an insufficient amount of time to live-migrate all virtual machines of the first plurality of virtual machines; querying, by the first controller, a network power system to obtain network power-related information, the network power system powering a network with a first data transfer path from the first set of powered hardware components to a second set of powered hardware components, where the first data transfer path is one of a plurality of data transfer paths, where the network power system powering the network is different from the one or more first power systems powering the first set of powered hardware components and is different from one or more second power systems powering the second set of powered hardware components, where the first set of powered hardware components and the second set of powered hardware components are in separate geographically-separated data centers, with the network being separate from and disposed between the separate geographically-separated data centers, and where an intermediary set of powered hardware components is employed across the plurality of data transfer paths; based on determining that the estimated amount of time to power failure is an insufficient amount of time to live-migrate all virtual machines of the first plurality of virtual machines: referencing historical migrating data relating to an amount of migration time required to migrate one or more virtual machines; referencing historical snapshotting data relating to an amount of snapshotting time required to snapshot one or more virtual machines; selecting, by the first controller, a first subset of one or more virtual machines of the first plurality of virtual machines that is eligible to be live-migrated through one or more switches along the first data transfer path from the first set of powered hardware components to the second set of powered hardware components, based on the referenced historical migrating data; and selecting, by the first controller, a snapshot for a second subset of one or more virtual machines of the first plurality of virtual machines that is eligible to be created and subsequently forwarded to the intermediary set of powered hardware components located between the first set of powered hardware components and the second set of powered hardware components, based on the referenced historical snapshotting data; dynamically generating, by the first controller, a relocation protocol for migrating the first plurality of virtual machines based, at least in part, upon the first power-related information and the network power-related information, the relocation protocol being an emergency relocation protocol dynamically generated based, at least in part, on the estimated amount of time to power failure to the first set of powered hardware components being insufficient to live-migrate all virtual machines of the first plurality of virtual machines, and the dynamically generating comprising assigning, by the first controller, a virtual machine of the first plurality of virtual machines to the first subset of one or more virtual machines of the first plurality of virtual machines to be live migrated or the second subset of one or more virtual machines of the first plurality of virtual machines to be snapshotted for migration, the assigning being based, at least in part, upon 1) the obtained first power-related information, 2) the queried network power-related information, 3) the estimated amount of time to power failure, 4) the selection of the first subset of one or more virtual machines of the first plurality of virtual machines is eligible to be live-migrated, and 5) the selection of the snapshot for the second subset of one or more virtual machines of the first plurality of virtual machines is eligible to be created and transmitted to the intermediary set of powered hardware components; performing, within one of the data centers, a series of actions within the relocation protocol, the series of actions consisting of: a live migration of the first subset of one or more virtual machines of the first plurality of virtual machines comprising a transfer of the first subset of one or more virtual machines of the first plurality of virtual machines through one or more direct switches of the first data transfer path from the first set of powered hardware components to the second set of powered hardware components, where the first subset of virtual machine(s) is migrated to and runs on the second set of powered hardware components, and where the first subset of virtual machine(s) continues to operate through the live migration; and a snapshotting of the second subset of one or more virtual machines of the first plurality of virtual machines comprising a forwarding of snapshot data associated with the second subset of one or more virtual machines of the first plurality of virtual machines from the first set of powered hardware components to the intermediary set of powered hardware components through one or more intermediate switches on a different data transfer path of the plurality of data transfer paths separate from the first data transfer path; and migrating the first plurality of virtual machines, by performing the relocation protocol, to the second set of powered hardware components.
 2. The computer-implemented method of claim 1, wherein the migrating comprises: migrating the second subset of virtual machine(s) by, at least in part, deploying the second subset of virtual machine(s) to the second set of powered hardware components based on respective snapshot(s) of the second subset of virtual machine(s) obtained at the first set of powered hardware components.
 3. The computer-implemented method of claim 2, wherein the migrating of the second subset of virtual machine(s) is performed after completion of the migrating of the first subset of virtual machine(s).
 4. The computer-implemented method of claim 2, wherein the migrating the second subset of virtual machine(s) includes first transferring the respective snapshot(s) of the virtual machine(s) of the second subset of virtual machine(s) to the intermediary set of powered hardware components powered by an intermediary power system set before deploying the second subset of virtual machine(s) to the second set of powered hardware components based on their respective snapshot(s), the intermediary power system set being different from the first power system set.
 5. The computer-implemented method of claim 4, wherein the transferring the respective snapshot(s) of the virtual machine(s) of the second subset of virtual machine(s) to the intermediary set of powered hardware components occurs concurrent with the migrating of the first subset of virtual machine(s) to the second set of powered hardware components.
 6. The computer-implemented method of claim 2, wherein the first set of powered hardware components are of a first cloud, the first controller being a first cloud controller, and the second set of powered hardware components are of a second cloud, the second set of powered hardware components being powered from a second power system set comprising the one or more second power systems.
 7. The computer-implemented method of claim 6, wherein the first cloud and the second cloud are hosted in the different, geographically-separated data centers.
 8. The computer-implemented method of claim 6, wherein the second cloud includes a second cloud controller, and the generating further comprises obtaining, by the first cloud controller, second power-related information from the second cloud controller or the second power system set indicative of power status to the second set of powered hardware components.
 9. The computer-implemented method of claim 1, wherein the generating, by the first controller, the relocation protocol includes referencing historical data relating to at least one of virtual machine migrating or virtual machine snapshotting to facilitate placing at least one virtual machine of the first plurality of virtual machines in either the first subset of virtual machine(s) or the second subset of virtual machine(s).
 10. The computer-implemented method of claim 1, wherein the generating, by the first controller, the relocation protocol includes using associated priority information of at least one virtual machine of the first plurality of virtual machines in placing the at least one virtual machine in either the first subset of virtual machine(s) or the second subset of virtual machine(s).
 11. The computer-implemented method of claim 1, wherein the obtaining, by the first controller, the network power-related information includes determining power status to one or more network switches of the network in the first data transfer path from the first set of powered hardware components to the second set of powered hardware components.
 12. A system for facilitating relocating virtual machines, the system comprising: a memory; and a processing circuit communicatively coupled with the memory, wherein the system performs a method comprising: obtaining, by a first controller, first power-related information from a first power system set comprising one or more first power systems powering a first set of powered hardware components with which the first controller is associated, the first set of powered hardware components running a first plurality of virtual machines, and the first power-related information including an estimated amount of time to power failure to the first set of powered hardware components; determining, by the first controller, that the estimated amount of time to power failure is an insufficient amount of time to live-migrate all virtual machines of the first plurality of virtual machines; querying, by the first controller, a network power system to obtain network power-related information, the network power system powering a network with a first data transfer path from the first set of powered hardware components to a second set of powered hardware components, where the first data transfer path is one of a plurality of data transfer paths, where the network power system powering the network is different from the one or more first power systems powering the first set of powered hardware components and is different from one or more second power systems powering the second set of powered hardware components, where the first set of powered hardware components and the second set of powered hardware components are in separate geographically-separated data centers, with the network being separate from and disposed between the separate geographically-separated data centers, and where an intermediary set of powered hardware components is employed across the plurality of data transfer paths; based on determining that the estimated amount of time to power failure is an insufficient amount of time to live-migrate all virtual machines of the first plurality of virtual machines: referencing historical migrating data relating to an amount of migration time required to migrate one or more virtual machines; referencing historical snapshotting data relating to an amount of snapshotting time required to snapshot one or more virtual machines; selecting, by the first controller, a first subset of one or more virtual machines of the first plurality of virtual machines that is eligible to be live-migrated through one or more switches along the first data transfer path from the first set of powered hardware components to the second set of powered hardware components, based on the referenced historical migrating data; and selecting, by the first controller, a snapshot for a second subset of one or more virtual machines of the first plurality of virtual machines that is eligible to be created and subsequently forwarded to the intermediary set of powered hardware components located between the first set of powered hardware components and the second set of powered hardware components, based on the referenced historical snapshotting data; dynamically generating, by the first controller, a relocation protocol for migrating the first plurality of virtual machines based, at least in part, upon the first power-related information and the network power-related information, the relocation protocol being an emergency relocation protocol dynamically generated based, at least in part, on the estimated amount of time to power failure to the first set of powered hardware components being insufficient to live-migrate all virtual machines of the first plurality of virtual machines, and the dynamically generating comprising assigning, by the first controller, a virtual machine of the first plurality of virtual machines to the first subset of one or more virtual machines of the first plurality of virtual machines to be live migrated or the second subset of one or more virtual machines of the first plurality of virtual machines to be snapshotted for migration, the assigning being based, at least in part, upon 1) the obtained first power-related information, 2) the queried network power-related information, 3) the estimated amount of time to power failure, 4) the selection of the first subset of one or more virtual machines of the first plurality of virtual machines is eligible to be live-migrated, and 5) the selection of the snapshot for the second subset of one or more virtual machines of the first plurality of virtual machines is eligible to be created and transmitted to the intermediary set of powered hardware components; performing, within one of the data centers, a series of actions within the relocation protocol, the series of actions consisting of: a live migration of the first subset of one or more virtual machines of the first plurality of virtual machines comprising a transfer of the first subset of one or more virtual machines of the first plurality of virtual machines through one or more direct switches of the first data transfer path from the first set of powered hardware components to the second set of powered hardware components, where the first subset of virtual machine(s) is migrated to and runs on the second set of powered hardware components, and where the first subset of virtual machine(s) continues to operate through the live migration; and a snapshotting of the second subset of one or more virtual machines of the first plurality of virtual machines comprising a forwarding of snapshot data associated with the second subset of one or more virtual machines of the first plurality of virtual machines from the first set of powered hardware components to the intermediary set of powered hardware components through one or more intermediate switches on a different data transfer path of the plurality of data transfer paths separate from the first data transfer path; and migrating the first plurality of virtual machines, by performing the relocation protocol, to the second set of powered hardware components.
 13. The system of claim 12, wherein the migrating comprises: migrating the second subset of virtual machine(s) by, at least in part, deploying the second subset of virtual machine(s) to the second set of powered hardware components based on respective snapshot(s) of the second subset of virtual machine(s) obtained at the first set of powered hardware components.
 14. The system of claim 13, wherein the migrating of the second subset of virtual machine(s) is performed after completion of the migrating of the first subset of virtual machine(s).
 15. The system of claim 13, wherein: the migrating the second subset of virtual machine(s) includes first transferring the respective snapshot(s) of the virtual machine(s) of the second subset of virtual machine(s) to the intermediary set of powered hardware components powered by an intermediary power system set before deploying the second subset of virtual machine(s) to the second set of powered hardware components based on their respective snapshot(s), the intermediary power system set being different from the first power system set; and the transferring of the respective snapshot(s) of the virtual machine(s) of the second subset of virtual machine(s) to the intermediary set of powered hardware components occurs concurrent with the migrating of the first subset of virtual machine(s) to the second set of powered hardware components.
 16. The system of claim 13, wherein the first set of powered hardware components are of a first cloud, the first controller being a first cloud controller, and the second set of powered hardware components are of a second cloud, the second set of powered hardware components being powered from a second power system set comprising the one or more second power systems.
 17. The system of claim 16, wherein the second cloud includes a second cloud controller, and the generating further comprises obtaining, by the first cloud controller, second power-related information from the second cloud controller or the second power system set indicative of power status to the second set of powered hardware components.
 18. The system of claim 12, wherein the generating, by the first controller, the relocation protocol includes referencing information selected from a set consisting of historical data relating to at least one of virtual machine migrating or virtual machine snapshotting, or associated priority information of at least one virtual machine of the first plurality of virtual machines, the referencing information facilitating placing at least one virtual machine in either the first subset of virtual machine(s) or the second subset of virtual machine(s).
 19. A computer program product for facilitating relocating virtual machines, the computer program product comprising: a non-transitory computer-readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising: obtaining, by a first controller, first power-related information from a first power system set comprising one or more first power systems powering a first set of powered hardware components with which the first controller is associated, the first set of powered hardware components running a first plurality of virtual machines, and the first power-related information including an estimated amount of time to power failure to the first set of powered hardware components; determining, by the first controller, that the estimated amount of time to power failure is an insufficient amount of time to live-migrate all virtual machines of the first plurality of virtual machines; querying, by the first controller, a network power system to obtain network power-related information, the network power system powering a network with a first data transfer path from the first set of powered hardware components to a second set of powered hardware components, where the first data transfer path is one of a plurality of data transfer paths, where the network power system powering the network is different from the one or more first power systems powering the first set of powered hardware components and is different from one or more second power systems powering the second set of powered hardware components, where the first set of powered hardware components and the second set of powered hardware components are in separate geographically-separated data centers, with the network being separate from and disposed between the separate geographically-separated data centers, and where an intermediary set of powered hardware components is employed across the plurality of data transfer paths; based on determining that the estimated amount of time to power failure is an insufficient amount of time to live-migrate all virtual machines of the first plurality of virtual machines: referencing historical migrating data relating to an amount of migration time required to migrate one or more virtual machines; referencing historical snapshotting data relating to an amount of snapshotting time required to snapshot one or more virtual machines; selecting, by the first controller, a first subset of one or more virtual machines of the first plurality of virtual machines that is eligible to be live-migrated through one or more switches along the first data transfer path from the first set of powered hardware components to the second set of powered hardware components, based on the referenced historical migrating data; and selecting, by the first controller, a snapshot for a second subset of one or more virtual machines of the first plurality of virtual machines that is eligible to be created and subsequently forwarded to the intermediary set of powered hardware components located between the first set of powered hardware components and the second set of powered hardware components, based on the referenced historical snapshotting data; dynamically generating, by the first controller, a relocation protocol for migrating the first plurality of virtual machines based, at least in part, upon the first power-related information and the network power-related information, the relocation protocol being an emergency relocation protocol dynamically generated based, at least in part, on the estimated amount of time to power failure to the first set of powered hardware components being insufficient to live-migrate all virtual machines of the first plurality of virtual machines, and the dynamically generating comprising assigning, by the first controller, a virtual machine of the first plurality of virtual machines to the first subset of one or more virtual machines of the first plurality of virtual machines to be live migrated or the second subset of one or more virtual machines of the first plurality of virtual machines to be snapshotted for migration, the assigning being based, at least in part, upon 1) the obtained first power-related information, 2) the queried network power-related information, 3) the estimated amount of time to power failure, 4) the selection of the first subset of one or more virtual machines of the first plurality of virtual machines is eligible to be live-migrated, and 5) the selection of the snapshot for the second subset of one or more virtual machines of the first plurality of virtual machines is eligible to be created and transmitted to the intermediary set of powered hardware components; performing, within one of the data centers, a series of actions within the relocation protocol, the series of actions consisting of: a live migration of the first subset of one or more virtual machines of the first plurality of virtual machines comprising a transfer of the first subset of one or more virtual machines of the first plurality of virtual machines through one or more direct switches of the first data transfer path from the first set of powered hardware components to the second set of powered hardware components, where the first subset of virtual machine(s) is migrated to and runs on the second set of powered hardware components, and where the first subset of virtual machine(s) continues to operate through the live migration; and a snapshotting of the second subset of one or more virtual machines of the first plurality of virtual machines comprising a forwarding of snapshot data associated with the second subset of one or more virtual machines of the first plurality of virtual machines from the first set of powered hardware components to the intermediary set of powered hardware components through one or more intermediate switches on a different data transfer path of the plurality of data transfer paths separate from the first data transfer path; and migrating the first plurality of virtual machines, by performing the relocation protocol, to the second set of powered hardware components.
 20. The computer program product of claim 19, wherein the migration comprises: migrating the second subset of virtual machine(s) by, at least in part, deploying the second subset of virtual machine(s) to the second set of powered hardware components based on respective snapshot(s) of the second subset of virtual machine(s) obtained at the first set of powered hardware components. 